Skip to content

Background tasks: advanced settings docs#61

Open
mattsodomsky wants to merge 4 commits into
mainfrom
task-background-lane
Open

Background tasks: advanced settings docs#61
mattsodomsky wants to merge 4 commits into
mainfrom
task-background-lane

Conversation

@mattsodomsky

@mattsodomsky mattsodomsky commented Jul 5, 2026

Copy link
Copy Markdown
Member

Documentation for the background lane and per-task concurrency caps (lightward/mechanic-api#2290, lightward/mechanic-ui#2051).

New page at core/tasks/advanced-settings/background-tasks.md — the URL both UI "Learn more" links point to. Covers:

  • The yield contract in merchant terms ("background runs wait until your other tasks are caught up"), including that busy shops may pause background work entirely and that this is the setting working, not a stuck task.
  • Guaranteed progress (a run waiting for hours is periodically given a slot — deliberately phrased without pinning the exact threshold or cooldown).
  • Manual retries re-enter the queue with the task's current settings (an earlier draft claimed a bypass that matched no code).
  • Immediate reclassification of already-queued runs, both directions.
  • An explicit statement that nothing is ever dropped — background runs queue without limit; the setting changes when they run, never whether.
  • The bulk-operations expiry caveat as a warning hint (link path verified against the docs tree).
  • Maximum concurrent runs, and how it differs from (and combines with) the background setting.

⚠️ Hold merge until mechanic-api#2290 deploys — GitBook publishes main immediately, and this describes behavior that doesn't exist yet.

🤖 Generated with Claude Code

mattsodomsky and others added 2 commits July 5, 2026 10:08
Documents the background lane and per-task concurrency caps shipping in
lightward/mechanic-api#2290: the yield contract, immediate reclassification
of queued runs, the guaranteed-progress drip, the backlog limit, and the
bulk-operations expiry caveat.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The backlog cap was removed from the implementation
(lightward/mechanic-api#2290): background runs queue without limit,
like everything else in Mechanic. Say so explicitly.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@mattsodomsky

Copy link
Copy Markdown
Member Author

Tracking issue with the full rollout checklist: lightward/mechanic-api#2293

Fix the dead bulk-operations link; the valve grants periodic (not
per-slot) progress; manual retries re-enter the queue with the task's
current settings rather than bypassing them; large-backlog lane changes
take moments, not zero time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant